Skip to content

fix(deps): Bump Groovy to 4.0.32#15671

Open
jamesfredley wants to merge 1 commit into
8.0.xfrom
deps/groovy-4.0.32
Open

fix(deps): Bump Groovy to 4.0.32#15671
jamesfredley wants to merge 1 commit into
8.0.xfrom
deps/groovy-4.0.32

Conversation

@jamesfredley
Copy link
Copy Markdown
Contributor

Brings 8.0.x's Groovy 4 pin in line with 7.0.x, which moved to 4.0.32 in 9917b129fb ("fix(deps): Bump Groovy to 4.0.32").

On 8.0.x both groovy.version and gradle-groovy.version are held at the same value today, so both are bumped together.

Apache Groovy 4.0.32 is on Maven Central:

Verified locally on JDK 21:

./gradlew :grails-core:compileGroovy :grails-bootstrap:compileGroovy \
          validateDependencyVersions --refresh-dependencies
-> BUILD SUCCESSFUL in 1m 17s (198 actionable tasks)

Once merged, this propagates to the stacked Groovy 5 (#15557) and Groovy 6 canary (#15558) PRs via the usual base-sync.

Brings 8.0.x's Groovy 4 pin in line with 7.0.x, which moved to 4.0.32
in 9917b12. Both `groovy.version` and `gradle-groovy.version` are
held at the same value on 8.0.x today, so bump both.

Apache Groovy 4.0.32 is on Maven Central:
  https://repo1.maven.org/maven2/org/apache/groovy/groovy/4.0.32/
  https://repo1.maven.org/maven2/org/apache/groovy/groovy-bom/4.0.32/

Verified locally:
  ./gradlew :grails-core:compileGroovy :grails-bootstrap:compileGroovy \
            validateDependencyVersions --refresh-dependencies
  -> BUILD SUCCESSFUL

Assisted-by: opencode:claude-4.7-opus
Copilot AI review requested due to automatic review settings May 20, 2026 18:23
@jamesfredley jamesfredley self-assigned this May 20, 2026
@jamesfredley jamesfredley added this to the grails:8.0.0-M2 milestone May 20, 2026
@jamesfredley jamesfredley moved this to In Progress in Apache Grails May 20, 2026
@jamesfredley jamesfredley requested review from jdaugherty and matrei May 20, 2026 18:27
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@testlens-app
Copy link
Copy Markdown

testlens-app Bot commented May 20, 2026

🚨 TestLens detected 2 failed tests 🚨

Here is what you can do:

  1. Inspect the test failures carefully.
  2. If you are convinced that some of the tests are flaky, you can mute them below.
  3. Finally, trigger a rerun by checking the rerun checkbox.

Test Summary

Check Project/Task Test Runs
CI - Groovy Joint Validation Build / build_grails :grails-data-hibernate5-dbmigration:test GroovyChangeLogSpec > outputs a warning message by calling the warn method
CI - Groovy Joint Validation Build / build_grails :grails-data-hibernate5-dbmigration:test GroovyChangeLogSpec > updates a database with Groovy Change

🏷️ Commit: d393183
▶️ Tests: 36071 executed
🟡 Checks: 35/36 completed

Test Failures

GroovyChangeLogSpec > outputs a warning message by calling the warn method (:grails-data-hibernate5-dbmigration:test in CI - Groovy Joint Validation Build / build_grails)
Condition not satisfied:

output.toString().contains('warn message')
|      |          |
|      |          false
|      19:25:45.693 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
|      Running Changeset: changelog.groovy::2::John Smith
|       
|      UPDATE SUMMARY
|      Run:                          1
|      Previously run:               0
|      Filtered out:                 0
|      -------------------------------
|      Total change sets:            1
|       
|      Liquibase: Update has been successful. Rows affected: 1
19:25:45.693 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
Running Changeset: changelog.groovy::2::John Smith
 
UPDATE SUMMARY
Run:                          1
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:            1
 
Liquibase: Update has been successful. Rows affected: 1

	at org.grails.plugins.databasemigration.liquibase.GroovyChangeLogSpec.outputs a warning message by calling the warn method(GroovyChangeLogSpec.groovy:87)
GroovyChangeLogSpec > updates a database with Groovy Change (:grails-data-hibernate5-dbmigration:test in CI - Groovy Joint Validation Build / build_grails)
Condition not satisfied:

output.toString().contains('confirmation message')
|      |          |
|      |          false
|      19:25:45.082 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
|      Running Changeset: changelog.groovy::1::John Smith
|       
|      UPDATE SUMMARY
|      Run:                          1
|      Previously run:               0
|      Filtered out:                 0
|      -------------------------------
|      Total change sets:            1
|       
|      Liquibase: Update has been successful. Rows affected: 1
19:25:45.082 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
Running Changeset: changelog.groovy::1::John Smith
 
UPDATE SUMMARY
Run:                          1
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:            1
 
Liquibase: Update has been successful. Rows affected: 1

	at org.grails.plugins.databasemigration.liquibase.GroovyChangeLogSpec.updates a database with Groovy Change(GroovyChangeLogSpec.groovy:61)

Muted Tests

Note

Checks are currently running using the configuration below.

Select tests to mute in this pull request:

🔲 GroovyChangeLogSpec > outputs a warning message by calling the warn method
🔲 GroovyChangeLogSpec > updates a database with Groovy Change

Reuse successful test results:

🔲 ♻️ Only rerun the tests that failed or were muted before

Click the checkbox to trigger a rerun:

🔲 Rerun jobs


Learn more about TestLens at testlens.app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants